Skip to content

fix: normalize image billing inputs - #7

Merged
3metaJun merged 1 commit into
metaproxy/v1.0.0-rc.21from
fix/normalize-image-billing-input
Aug 30, 2026
Merged

fix: normalize image billing inputs#7
3metaJun merged 1 commit into
metaproxy/v1.0.0-rc.21from
fix/normalize-image-billing-input

Conversation

@3metaJun

Copy link
Copy Markdown
Owner

Image billing expressions currently see raw request fields, so invalid/defaulted n and provider-specific sizes can produce the wrong quota.

This change:

  • feeds validated/defaulted image counts into billing expressions
  • normalizes image sizes to the same 1K/2K/4K buckets used by the upstream
  • preserves custom request fields in live and channel-test paths
  • rejects non-object image billing bodies without panicking

Verification:

  • go test ./dto ./relay/helper ./controller ./model ./relay/channel/minimax
  • git diff --check
  • Independent review: PASS (gpt-5.6-sol, medium)

Agent: gpt-5.6-sol via T3 Code
Review: gpt-5.6-sol (medium) via T3 Code

@3metaJun
3metaJun merged commit ee0d23f into metaproxy/v1.0.0-rc.21 Aug 30, 2026
1 check passed
@3metaJun
3metaJun deleted the fix/normalize-image-billing-input branch August 30, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant